-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
|
A little confused on how should we use import. This is how it is used on UI. and then it needs to be used as a param in required config rules as such: But terraform doesn't allow for the syntax |
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
|
/run pipeline |
1 similar comment
|
/run pipeline |
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left some comments - also need to resolve conflict (don't bump common-dev-assets version in the PR unless you explicitly need a new version, otherwise you end up with conflict after renovate runs)
modules/rules/outputs.tf
Outdated
| @@ -0,0 +1,4 @@ | |||
| output "rule_ids" { | |||
| description = "The ids for the rules created by this module." | |||
| value = [for rule in resource.ibm_scc_rule.scc_rule_instance : rule.rule_id] | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does this output look like? If its just a list of rule IDs that not much use. Ideally needs to have a mapping to the rule name so users can lookup the rule ID using the rule name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name doesn't exist in outputs https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_rule#attribute-reference
|
/run pipeline |
|
No plans to implement |
Description
Add a rules submodule in modules/rules that should support creating multiple custom rules.
#48
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Add a rules submodule in modules/rules that should support creating multiple custom rules.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers